TODO:
We want a very sophisticated code examination here with good explanations
on where to look for an illegal instruction or such.
Only after that we should try to build an InstructionList and throw an
AssertionViolatedException if after our examination InstructionList building
still fails.
That examination should be implemented in a byte-oriented way, i.e. look for
an instruction, make sure its validity, count its length, find the next
instruction and so on.