Faster to read, and keeps the reader's mind at a semantically higher level.

I disagree. If you've progressed beyond the absolute beginner phase you know exactly what that line is when you see it. You've only put in work to obfuscate your code a bit and (potentially) cause conflicts with other units whose author had the same idea.

Provided that he knows about the macro. Otherwise it's slower and if you switch projects often it requires that you remember what's it about.

I guess it could be useful for teams working together on bigger codebases.

1. An appropriate named macro shouldn't cause you to need to investigate it unnecessarily

2 most IDEs allow simple hover over and see macro definition without having to break much flow.

I might go a step further and append "an appropriately implemented macro". Just because something has a good name doesn't mean it's not filled with crazy.

Otherwise I totally agree with your point.

If the macro is named appropriately, you don't have to go look up anything. And even if you do, you do it once (per project perhaps). No big deal.

I mean, you don't go look up the definitions of every function that gets called, every time they are called, right?