Currently, we have several binding recipe operators that have 2 interpretations, depending on whether they are used to 'box' or 'unbox'. These operators are MOVE, DEREFERENCE, and CONVERT_ADDRESS.

This dual purpose is hard to document and explain, also because the concept of 'box' and 'unbox' is half-formed.

As a solution, we could split those operators in 2 operators each, so that each operator has only 1 interpretation. This will also help simplify the implementing code, since there is no more need to have 2 verify, interpret, and specialize for each operator (which are the same for the others).