The capability of running ram at a speed is part of the testing process as the memory controller is part of a cpu, if for whatever reason the ram wasnt stable without excessive work (which manually tuning timings is) they should have simply downclocked the ram.
So e.g. if ram is stable at 3200 on intel in XMP, then by all means test at 3200, but if the same ram on AMD only works with those timings at 2933, then the fair thing to do is test at 2933, and the performance hit is part and parcel of what users can reasonable expect. It is why I am not surprised we have users on ocuk, trying to get their ram stable at the speed reviewers like GN tested at, as they were given a false picture of AMD's capabilities.
I checked back on GN's AMD review and he didnt disclose he had trouble getting the ram to work. The first time I knew of him having issues was when he told the PT guy in that interview.
Clearly there is disagreement here on what is considered a fair way of testing, but my view wont change, I feel if you doing things like whacking fans to 100% to avoid thermal throttling, and manually tuning ram to get by performance ceilings, then its beyond fair testing.
Ironically the way I think things should be tested actually favours AMD which is to test ram at supported speeds which is a case where AMD would get better ram performance as they support higher speeds than intel. Either that or go for ram as fast as possible, but if a cpu cannot reasonably handle it then drop down the speed even if its slower than the competitor.