I'm inclined to believe that I'm also still experiencing this with MSVC 19.43.34808.0, has this been resolved or reported upstream?