My policy on code reviews is: my brain is a bad interpreter. Either I run the code and see that it works, I trust the tests (see #1 why this doesn't work), or I rubber stamp it and move on. Which I do mostly boils down to what the risk/impact of a bug in that part of code would be, and I've been around long enough to have developed the intuition to usually be right.
