This is basically standard Objective-C assert. While we could always pass it as an option, i believe it makes perfect sense to warn on it by default.
The same applies to NSCAssert which drops additional support for displaying Objective-C method information so it acts exactly like C assert.
I tested it on live code with actual Foundation headers and it seems to work correctly out of the box.
I'm also interested in making an even more agressive step in this direction and adding an option to accept any macro that ends with "...assert" suffix, case-insensitively. This would probably go under an off-by-default flag. Would this be acceptable?