If it was redundant, it wouldn't be needed in general - it doesn't matter if you removed it because of profiling on program X, or Y - as long as the code is correct, it would be a right thing to do.<p>If the list of features is set and you're not doing a complete refactoring (only 10 or so lines out of several thousands were changed), I don't see a problem with this approach. You can (/should) always go back to the profiler if you find a better test case...