tcallin, Thank you for pointing out this bug fix, we have had issues in this area and will see if it makes sense for us to apply the proc change.
Just an FYI, the modified proc is using invalid logic to determine leap years. A leap year is not defined only by being a year divisible evenly by 4. Instead a leap year is divisible evenly by 4 but if that year is evenly divisible by 100, than it is not a leap year unless that year is also evenly divisible by 400.
For the sake of the 1 or 2 lines of extra code, MAS500 logic could stand the test of time instead of assuming it's logic will never be ported to some functioning entity in 2100. Think Y2K. 
