The problem with his example `retweet_count` is the blanket statement in the API:

    The timeline returned is the equivalent of the one seen when you view a user's profile on twitter.com.

Thus:

- the value is capped at 100 (since the retweet count is displayed up to 100)

- the value can be "100+" (https://twitter.com/#!/SEGA/status/144219968773423104 says "Retweeted by ivucica and 100+ others")

Now, I don't disagree that the documentation should explain retweet_count more clearly, but I'm surprised that people trip up on this particular issue.