Application Uninstall Evaluation Delay
Using some native application uninstallers they appear to complete, i.e. successful execution, before the uninstall process actually completes (typically a secondary uninstall process has been launched). This then triggers the Application evaluation which sees the Application is still present, i.e. files or registry settings still present, and so fails the uninstall. However at the next Application evaluation the uninstall has completed and the Application is successfully evaluated as uninstalled. This could be prevented if a delay could be configured between the uninstall "completing" and the Application evaluation running. This can be done with scripts of course but you basically wind up writing your own application detection routines before passing it back to SCCM to repeat the same whereas a simple configurable delay in evaluation would fix the issue.