An Object is a virtual entity that physically can be constituted by sparse contents anywhere in the memory, so it’s not a continuous stream of bytes you can copy/past anywhere. People desiring such capability need to implement what is called “serialization”, that means grab an frozen state of an object and convert its properties to a series of bytes that can be deserialized later into a copy of that prior object.
Note that Structures behave differently from Objects. When you assign a Structure, you create a copy. This is true whether you pass it as a parameter to a function (unless you use ByRef) or assign it to a different local variable.
Yes, I’m aware of the copy aspect; which is not a problem for me. What concerns me more is efficiency on the M2 processor for things like storing, reading doubles that may or may not be aligned to say 2 or 4 byte offsets. I’m not sure if it matters or I should care.