> or the most succinct (replace && by & if writing):

That is strictly not necessary. `auto&&` is what is now being called a universal reference: `item` resolves to `const int&` if `myVec` is const, and to `int&` if `myVec` is mutable. `auto&&` does the right thing in the majority of cases. In fact, the following extension [1] has been proposed for C++17 (and already implemented in recent clang builds):

    for( item : myVec ) { /* do stuff */ }

which is meant to be a short-hand for

    for( auto&& item : myVec ) { /* do stuff */ }

[1] http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n399...