The problem can cause function calls to be misdirected, and has lead to many wasted hours debugging the wrong issue.

This sample code reproduced the problem in 17.13.0 but not in 17.14.2.

The problem is resolved by updating Visual Studio 2022 to the latest version.