LocalDatePattern.Parse throws IndexOutOfRangeException on some dates that match format but are not real dates

Given a date string like "00/15/1984" and a local date pattern created with the format "M/d/yyyy", calling format.Parse(dateString) throws an index out of range exception, rather than simply returning a failed ParseResult<LocalDate>. 

We haven't tested other Noda pattern types for the same behavior, but wouldn't be surprised if it's there as well.
