There should be a better way for advanced users to update at least notes on the Language Reference functions listing ANY quirky caveats and possibly function code execution time in clocks. Of course near the bottom of the page in the individual functions, so as to the noobs don't get confused or overwhelmed with caveats of a particular function, but allows novices and more advanced users writing time intensive loops to be aware of a functions quirks or execution time so they don't spend DAYS googling and reading through endless forum posts to find out that they must use direct port manipulation, or bit shifting instead of dividing using "/".
It's frustrating enough when you have the time to try different ways of coding the same function, but if you only have a few hrs during each day to debug your code to find a simple caveat of say digitalRead() was causing the issue the WHOLE time, is annoying.
Can we implement this standard on the language reference and save MANY unnecessary forum posts?