Memory synchronisation during OOP

[tolauwae]

Changes to the memory are not forwarded to the drone. This means that calling primitives with pointers (start + length of string for example) may fail, as the memory is not kept in sync.

Reproduce

1. Start OOP
2. Change memory
3. Call a primitive that uses the altered memory

[carllocos]

This problem not only affects the memory but in general any change to the application state. If new primitives are introduced that may change global variables for instance, or if we later allow to proxy also non-primitive functions, those changes should also be reflected in the local VM.