Restricting login hours is very sticky.  Most systems need to be accessible 24x7, but still have tight security.  Most security attacks occur after the administrators have gone home for the day.  The only place Database Scanner can compare this information is to the logon hours restrictions on the NT accounts or in seeing who is logged on when a scan is run.  While it is nice to have this feature, I do not use it.  The vast majority of SQL Servers are run with standard security.  Since Database Scanner is run manually, checking login hours doesn't gain you anything because it will only detect what it finds when it is scanned and the person who would initiate the scan has already gone home for the day.

Database Scanner 3.0.1 1 2 3 4 5 6 7 8 9 10