schedules may now be specified with a resolution up to one second
fixed a bug causing schedules containing the "*/" notation would never
trigger
fixed a bug which would cause task-registration to fail if the "*/"
notation was used for the month
add the exception to the error-message if the configured task which should
run now caused an exception (should never happen because the function is
spawned)
added possibility to define lists of time-values and therefore changed the
separator to space or tab. lists of time-values are separated by comma.
check if each element of a schedule is correct or throw an error if the
task gets registered
parseInt every numeric value when parsing the schedule to avaoid
parseInting them every time we check if a task should run
updated to reflect recent changes (seconds-resolution and
time-value-lists)