@Electro Fan: That was a (long, but) interesting read. :-)
And I agree that, without more in-depth investigation, it is hard to tell what the main contributing factor(s) to this behaviour is/are.
This said, mine is more of a layman's perspective on the matter: in practice, the continuity mode on the BM789 is less useful than that on most decently-fast meters (e.g. 121GW, BM257s, Fluke 87V, Fluke 187/189, etc.).
And just to prove what I mean (and what actually compelled me to start this thread in the first place), I made a recording of me using the BM789 in continuity mode on a given board (the video also shows me using the BM257s, with no spurious beeps present):
https://youtu.be/ZibMm3JXq7II suggest paying particular attention to the 0:30 mark in the video, when I am probing a denser area on the board.
As you can see, the amount of spurious beeps in quick succession makes one unable to determine if there is continuity or not, unless one keeps the probe in a location for longer.
Also, based on the response I received from Brymen (basically, the same as LuisBe's), I am to believe this is intentional for "professional applications" where sub-100μs response time for continuity is needed.
I wonder what real-life usage scenarios for a handheld multimeter would require such crazy-fast response time (as opposed to, say, the 15ms for the BM235).
Is a human even able to tell the difference between the two response times in any given scenario?
Also, if the spurious beeps are a consequence of this fast response time, don't they actually negate the value of this feature?
In my latest response to Brymen, I queried if it may be possible to implement (through a FW update) an option for the user to switch between "crazy fast" and "decent fast" response times.
I will report any response I get.