Parser may accidentally recurse into nested type where it is not allowed

[Crypt32]

Sometimes, binary data contains unfortunate data that may look like a nested type where it is not allowed. This includes octet strings and implicitly tagged types. Parser doesn't deal with any schema, so it tries to enforce some logic (within reasonable constraints) to determine when we must not recurse. The bug is that implicitly tagged types (0x80-0x9f) are attempted to recurse and may result nested type discovery. Implicitly tagged types cannot have nested types.