Out of memory not caught be general exception handler

see: http://stackoverflow.com/questions/16184812/out-of-memory-exception-not-caught
Added a catch for out of memory.
Doesn't "fix" the out of memory problem, but means a less fatal crash.
tweek the image scaling code to fall inline with the android dev website to try and combat out of memory.

already added a catch for OOM error as per: http://stackoverflow.com/questions/16184812/out-of-memory-exception-not-caught
Extra checking that the retweet was a success & updating the correct cache

fixes #138 & #140
Added extra check that the result is not null. - seen a null pointer for this on crittersism
Update release notes
when deleting delete from both cache's
Correct error.  Status coming back doesn't have this flag set.
Do not hide the new tweet bar when you scroll down to before the new tweets.
Correct the getVisible status function to actually get the visible one.

There seems to be an issue around the views whereby even when the item is at the top of the list, it's not the one on show.
Whooops forgot to take out the else.

That would never work!
Merge pull request #141 from BlythMeister/BetaVersion

Fix/work around for fatal OOM on image views. & #138 & #140 fixes