That's not a counter-argument. Why don't you need to mock out the interfaces that you're not testing?
now I do take care to avoid writing tests that depend on other code's results that would be likely to change. This hasn't proven to be the problem I've so often been warned about though.
...or, you tested each thing individually, so only related tests break and you can quickly zero in on the problem. Isn't that easier?