From ukDevGroup - does it have rules for known ambigous functions (Beep)

Let me start by apologising for asking without RTFM first. We had a talk at our usergroup meeting where someone had been caught our by Beep appearing in Sysutils and windows with different signatures. Of course you get a compile error if you coded one and then added / moved the uses clause. It was agreed that it was beyond the IDE / Compiler to give you a hint and you the dev wouldn't know unless you know.

.... but I wondered if FixInsight may have rules to detect common issues like this or constants that could cause the same issue and offer fixes (e.g. explicit unit scoping).

Do it do this already (in which case I'll go back to the group to promote it)?