There is a weird bug in an initialization routine that causes a stack dump when I add the first element to a key->value mapping in a function. I'm not sure why. It was very stubborn to get rid of, and makes no sense.
The stack dump indicated an Add operation was causing the failure in an ensure. I created an empty value, in case there was something up with the (should be) identical null value in the Add function. Nope. I wound up initializing the map with a single key->value pair at compile time, then clearing that value when the initialization code ran. The stack dump is gone, but brand new bugs in a different area appeared. What fun.
Who doesn't love C++ expressed as blueprints?