Good points. However...
There's a huge difference between a "needing the ability to wade into an unknown code base and understand how it behaves" and "one of the finest tests of programming ability".
Perhaps Gates overstates the case slightly, but I would say that there is a strong correlation between "X is a good programmer" and "X is an effective code reviewer" -- and the ability to quickly and accurately read code and to understand deep, non-trivial properties of the code has a lot to do with being a good code reviewer.
I think Gates has a very valid point: there are lots of circumstances where you need the ability to wade into an unknown code base and understand how it behaves (and how it ought to behave). The ability to read through code and understand non-trivial properties of the code really takes some experience to develop -- that is directly relevant to code review, for example.