VM BinaryReader endianness different across samples.

[puff]

Need to implement a way to parse the VMBinaryReader methods. This is because the endianness of the VM resource stream changes across samples, likely due to different Eazfuscator.NET versions being used.
The order of the OR operators doesn't matter, it's the index of the byte array for each OR operation that matters.

Also need this for the VMMemoryStream's special ReadInt32 for opcodes/operands.

Instead of parsing, the VMBinaryReader endianness could be implemented using emulation, possibly from the Echo library.

[puff]

Looking more likely to be different per Eazfuscator.NET version, rather than per sample.