BUG: API Doesn't Return Seconds for Modified Time and Created Time

Issue:

The "getRecords" API method no longer returns seconds for the "Modified Time" and "Created Time" fields. This is a CRITICAL issue, because the "lastModified" filter in the API request IS accurate to the second; therefore, major sync errors can occur.

For example: If the modified time for my last record was 16:47:36, the getRecords method would return a "Modified Time" field like this:
<FL val="Modified Time"><![CDATA[2010-07-18 16:47]]>

(Note how it chops off the 36 seconds). If I then use this value to get everything newer (i.e., &lastModified=2010-07-18 16:47) , it would return this last record over and over again, since its real modified time (16:47:36) is technically after the time retrieved in the "Modified Time" field (16:47).

Steps to Reproduce:

Issue is easily reproducible, as it appears to affect all records returned using getRecords method (I haven't tested other methods). You'll see as in the above example that it chops the seconds off the "Modified Time" field.

Note: The example given in the API docs includes the seconds, so clearly this is a bug.

Expected Behavior:

The time stamp for the "Modified Time" and "Created Time" fields returned by the getRecords API method should include seconds. It should look like the API example: