Eric: 0.92.8 should address your issue. The problem arose because the time zone information database uses the rules for Chicago in for all of CST in the US. In 1936 Chicago (it seems at least in part for corrupt reasons) changed its time zone from CST to EST, then back to CST. This means that for Chicago there are 2 offsets between standard time and UTC. What's more, the last one in the list in the file is EST (which technically makes sense). As a result my assumption that the last time zone of a particular type (standard vs daylight) would be the best one to pick was wrong).
The use of Chicago to represent all of CST is also obviously wrong, as this was a glitch that was local to Chicago, but that is a problem for somebody else to take up with the maintainers of that database.