Looking at the documentation for custom allocators (Use a custom allocator | Collections | 6.6.0) it says that to create a NativeArray you have to use CollectionHelper.CreateNativeArray, and to dispose it you have to use CollectionHelper.Dispose. However, all other Native collection types seem to be usable normally by just sending in the allocator and disposing as normal. I’m wondering why NativeArray requires this special step, and if there’s any plans to fix that (if possible). This discrepancy is kind of annoying, because it effectively means that you have to re-write all native array creations (and disposings) in ‘normal user code’ if you want to change to a custom allocator.
NativeArray is in the engine, whereas the other collections including the allocator framework are in the Collections package. They would have to move the Collections package into the engine as a module (similar to what they did for Mathematics) to get around this.