MIssing smart rules&analyses 4 auto-selecting/advising +admin/reports/updates integration

Issue Summary

Basically a ''(very)'' good module, but not happy about what it practically does; with other words: presently a sophisticated manual method works better for me:
http://wi-ca.org/Drupal_modules_update

If one uses an alpha, beta or rc release, auto-select/advice should be the next alpha/beta/rc or official release.

If one uses a dev release, preferable a next/new alpha/beta/rc/official should be selected; continuing with the next dev if not any of them.

Some general rules could be both more specified and individualized ''(I'm sure others might follow other selection methods)''

Then there is an system-error in Drupal itself: About every half year, old dev versions are given a new data and going through the system as a new dev-release, what is completely FALSE.
I have many hundreds of modules, so I can't correct for this by looking into all those modules (both dev and other release per module) to find out which one is REALLY the newest. Sometimes there is an up to 2 years old official/beta/rc/alpha release, but who knows, maybe this was just newer as the original latest dev was from before such a release? Then its dangerous to change back, as there might have been an original very old dev too, just a day or so after such a release to correct a fatal error.
=>
Anyway; an automatic system to look inside those modules and find out if a dev release indeed is newer ''(minimal +1 day, or that users can say how many days; from -x to +x)'' than an alpha/beta/rc/official release?

Last point what for I'm not going to open a new topic: maybe integration with /admin/reports/updates? - so that Plugin Manager also can be used from there in some smart integration? Like that Plugin Manager auto-selects with new fields "x" behind the several releases per modules? Then users can change that for some reason per modules, before giving Plugin Manager the sign to download and install.

Best with the good work!