channelsPerSlave>1 configuration with child datasets hit allocator caching issue

In a Thor configuration with multiple channels handling rows with child datasets, the row managers per slave and the allocator caching mechanism conspire to cause the row destructor callback to fail to find it's cached allocator.

This was because each slave channel had it's own cache, but the roxiemem slave row managers were sharing the global one.