Fixed (or found the reason): Issue # 75

Found the reason behind the issue # 75. It's the OS assigning threads to different cores which sometimes run at different speeds momentarily. There are two ways to fix this. First is to put a small delay between method calling (in the test) in order to ensure that the first calling of the method gets executed first. The second way is to assign only one core to JAVA SE process on Windows Task Manager manually. Currently just added Thread.sleep(1) between method callings (between executor.execute(t1) and executor.execute(t2)).

This is just a minor commit I did while doing our project (EECE 310 Project). Hope this helps.