When the function name is not found in the VM, the linked actor is checked for the function. (The list of functions the actor has access to in its instructions is generated by the -function execution signals.3.5.1). The VM has a method called VM::call_function, which sets up a call stack using supplied arguments and runs the code.
One disadvantage to this approach is that counting the number of execute instructions becomes more difficult, as transferring control to the linked VM is treated as the execution of only one instruction. (Again, this is one of those problems that I didn't quite solve.)