Calling func(x) in C may as well be causing x to be cloned or have some other nasty side effects that are not immediately obvious from looking at the code. Similarly how one should always keep in mind the existence of macros when reading C code, one should also keep in mind the existence of constructors and casting operators with C++. That's hardly the hidden cost.
It is easier to write messy or obscure code in C++, especially for a novice programmer. But this has less to do with the language per se and more with established coding practices within specific team. If there is a hidden cost to C++, it is the fact that it requires higher level of competence. Not that it has constructors.
What I can't tell is how much extra code the compiler will generate at this point, and that is the problem.
> If there is a hidden cost to C++, it is the fact that it requires higher level of competence. Not that it has constructors.
I didn't say the cost is in the constructors. They're a symptom of the cost. The cost is creating the mental model of your app.
Sure, if the entire team consisted of C++ superstars, we might be able to get away with this. Given the team size on current games, (and the fact that superstars are rare) that's unlikely to be the case.