A _legacy method bites the dust

This was as easy as I had hoped. I think I will try to follow this approach, i.e. pick one _legacy method to eliminate and chase it throughout the code. This implies that for some methods a lot of files may change. However, as everything is focused on one particular change the patch itself should still be reasonably coherent.