boost::container::flat_map force_copy violates strict-aliasing rule about container HOT 1 OPEN

I bumped into a version of this problem that's reproducible on GCC trunk

#include <utility>
#include <boost/container/flat_map.hpp>

namespace bc = boost::container;

int main() {
    bc::flat_map<int, int> map {
        std::pair(0, 1),
        std::pair(1, 2),
        std::pair(2, 4)
    };

    if (map.size() != 3) {
        return 1;
    }

    int i = 0;
    for (const auto &[k, v] : map) {
        ++i;
    }
    if (i != 3) {
        return 2;
    }

    return 0;
}

When this is compiled with -O1 it runs as expected: i == 3 and the exit status is 0.
When compiled with -DBOOST_CONTAINER_DISABLE_FORCEINLINE -O2 the loop gets optimized away, i == 0 and the exit status is 2.

Here's a Compiler Explorer link showing the result: https://godbolt.org/z/7W5eGrKGE
Built with g++ (Compiler-Explorer-Build-gcc-181917d56c0cf4b8c1174a492a8157f4a12d1100-binutils-2.40) 14.0.0 20231219 (experimental)

from container.