Before creating DynamicJump, the FunctionCall got a register for a possible jump address. Now that is handled by DynamicJump and FunctionCall just needs the method, from which it determines the binaryCode address
not correctly handling integer objects yet
code climate inspired
just so we still know at compile time
seems to fit the layer much better as we really have a very reduced instruction set
