Modern integrated development environments (IDEs) make many software engineering tasks easier by providing automated programming support such as code completion and navigation. However, such support - and therefore IDEs as a whole - operate on one version of the code at a time, and leave handling of code history to external tools or plugins, such as EGit for Eclipse. For example, when a method is removed from a class, developers can no longer find the method through code completion. This forces developers to manually switch across different versions or resort to using external tools when they need to learn about previous code versions. We propose a novel approach of adding a temporal dimension to IDEs in the context of tasks that previously required manual switching across different code versions. Our approach enables code completion and navigation to operate on multiple versions at a time. Our short paper introduced the idea of temporal code completion and navigation, and a vision for how that idea may be realized. This paper realizes that vision by implementing and evaluating a prototype tool called Tempura. We demonstrate Tempura's scalability with three large Eclipse projects and evaluate Tempura's usability through a controlled user study. The study participants learned about the code history with more accuracy and in shorter time when using Tempura than EGit. Although the sample size was not large enough to provide statistical significance for all metrics, the results show a promising outlook for our approach.