[mattnewport]

I used to maintain EASTL. I think it's more accurate to describe it as an implementation of the STL than a replacement. As far as possible it is API compatible with the STL, the API differences are primarily in the allocator model and it is possible to write EASTL code that compiles against another STL implementation with fairly minimal changes, almost none if you're not using custom allocators. There are a few extensions / extra containers but we went to great lengths to keep as much of the API identical as possible.