I wasn't able to test this because I'm yet to come across a peer that has a non-zero dPingTime.  I'm not sure why this is, as I thought most nodes should support that by now.  It gets calculated like this: (((double)nPingUsecTime) / 1e6), so I interpreted that to mean its the number of seconds as a floating point.