The upstream change r336737 make the check too smart to fix the case where loop variable could be used as const auto&.
But for the case like below, changing to const auto _ will introduce an "unused" complier warning.
for (auto _ : state) { // no references in _. }
This patch omit this case, and it is safe to do it as the case is very rare.
I have seens this pattern now multiple times in various checks, we should have some utility wrapping the hasAnyName(MyList). (Just in general, does not need to happen with this check)