Suggested by @ Iko Knyphausen:

You are already highlighting instruction opcodes in RAM (and you can click on them to see the instruction in code – which is great), however, sometimes instruction pointers can be set to arguments instead of opcode (or even to data if DEP is off), resulting in a different instruction altogether. I could envision a little context information on hovering any byte in RAM showing the current meaning of a byte, e.g. opcode, register, or address, but also possible alternatives such as a register or address value interpreted as an opcode.