Ambiguity in the result of `symbolic_operand`

Some symbolic_operand will be marked as both code and data. This can be observed in almost every test case. Is there any reason for this ambiguity?

This seems like a bug to me.

Really, I'm not sure why we track Type as part of the symbolic_operand relation at all. Most consumers of symbolic_operand ignore it, and those that do use it should be able to trivially check code(Dest) or !code(Dest).