This is not strictly a memory leak, though you can view it as one (that's why it appears as "possibly lost").
Here's a minimal scenario that replicates the issue:
static int *global_data = nullptr;
int main(int, char**)
{
global_data = new int{9}; // allocated for the duration of the application
// we rely on the program exitting for deallocation
}
In this case, the memory is never lost (because you still have a pointer pointing to it). It is also never deallocated, so whether the data is a leak or not is debatable (and something that has been debated again and again on various forums).
That is why valgrind takes the middle ground on this one and says "possibly lost" (it is up to you to decide if this is a leak or not, depending on what you are trying to do).
In your concrete example, what is "possibly lost" is internal data of the stl implementation. There is nothing to worry about.