The libc++ Xcode>=5.1 runs into problems with such custom allocator wrapping because it considers allocator value_types pair<K,V> and pair<const K,V> as not identical. Since a std::map uses constant keys while most map templates don't ask them to be const the libc++ assertion regarding allocator identicality would trigger often.

With the sal-internal custom allocator removed AOO no longer needs the stlport-replacement headers to support the complexity of containers with non-default allocators. The problems above, their uselessness and the extra complexity introduced by the suggests that they should be removed. Since there are no intra-module uses (and exported symbols) for them everything still remains binary compatible.