SDK 1.3.0 and custom allocators

In previous SDK releases (pre-0.8), I had been defining and passing in my own custom memory allocator for the oculus runtime to utilize, which had required diving in to LibOVRKernel and calling OVR::System::Init/Destroy manually, etc..  The ability to pass in an allocator had been removed in 0.8, but somewhat surprisingly it hasn't resurfaced in the proper interface for the consumer SDK release.

I'm more than happy to not have to delve into LibOVRKernel to do this (especially since those projects don't build in VStudio 2010), and perhaps it's a little less critical for PC development, but for those of use keeping a close eye on our memory tracking/allocations, I'm surprised this hasn't come up more often.

When might we expect to see the ability to use a custom allocator again?