We already suppress such reports for inlined functions, we should then get the same behavior for macros.
The underlying reason is that the same macro, can be called from many different contexts, and nullability can only be expected in _some_ of them.
Assuming that the macro can return null in _all_ of them sometimes leads to a large number of false positives.
E.g. consider the test case for the dynamic cast implementation in macro: in such cases, the bug report is unwanted.
Tracked in rdar://36304776
This hides the other local variable.