If you implement the virtuals defined by Q_OBJECT yourself, bypassing moc, the missing Q_OBJECT warning still triggers. It's a very rare fringe case, of course ;) Reproducible: Always Steps to Reproduce: An example can be found e.g. in GammaRay, core/multisignalmapper.cpp, GammaRay::MultiSignalMapperPrivate. The most prominent example for this in Qt is QSignalSpy, which is excluded from this check already by being a template though.
Sounds like a good candidate for testing suppressions: Can you add to the file where the warning was reported: // clazy:excludeall=missing-qobject
Closing this as fixed, although // clazy:excludeall=missing-qobject is not an elegant solution implementing a better solution would be a lot of work for such edge case