Memory Pools

[space928]

It might help performance to allocate pools of remote memory for things such as setting remote strings. These are usually very small operations and currently every time a user updates an Omsi string, the remote memory allocator is called.

[space928]

For now I see little immediate need to work on this. With the way that MemArrays are designed and with the new asynchronous memory allocator, most users shouldn't have problems with string writing efficiency. It's also probably more complicated to implement than I initially thought, as Omsi would probably not be able to free objects allocated inside memory pools as the memory allocator won't know about them.