More Discriptive Exception Messages

[Cluedrew]

Feature request: When an illegal instruction is received (and kills the unit) I think a more descriptive error message should be included. I think this should include at least the operation, the value that is out of range (register A, B, C or the immediate), the value that was provided and the legal values for that argument.

[Labdabeta]

Exceptions are intended to be slowly removed from the game via explicit checks. Please let me know any exceptions you see and I will patch them one by one.

Create new issues for each new case including the following information and labelled as "Uncaught Exception" just like this one:

• A source code that when assembled produces the exception.
• The UT on which the exception occurs (the -x switch may help)

I will keep this issue open until such time as I am reasonably confident all such exceptions have been handled.